Transaction optimization through scanned data

ABSTRACT

Techniques are described for facilitating and/or optimizing a transaction, such as a purchase transaction, through the use of scanned data. In some implementations, a user may use a portable computing device to scan a vehicle tag (e.g., vehicle identification number) that is affixed to a vehicle and determine vehicle information. The user may also scan a user tag such as a driver&#39;s license to determine user data that identifies the user. The vehicle data and/or user data may be communicated to transaction service(s), which generate transaction data that may be specific to the particular user that provided the vehicle data and/or user data. The transaction data may include information regarding a price of the vehicle, terms of a loan that the user may take out to finance the purchase of the vehicle, information regarding an insurance policy for insuring the vehicle, and so forth.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of and claims priority toU.S. application Ser. No. 16/211,874, filed on Dec. 6, 2018, which is acontinuation application of and claims priority to U.S. application Ser.No. 15/711,459, titled “Transaction Optimization Through Scanned Data,”filed on Sep. 21, 2017, which is related to, and claims priority to,U.S. Provisional Patent Application Ser. No. 62/397,669, titled“Transaction Optimization Through Scanned Data,” which was filed on Sep.21, 2016, the entirety of which are incorporated by reference into thepresent disclosure.

BACKGROUND

For an average individual, purchasing a vehicle or other expensive itemmay be a stressful experience. The potential purchaser walking through ashowroom or a vehicle sales lot may be confronted with sales personnelwhose goal is to maximize the sale price and who may not necessarily befocused on the purchaser's concerns. Moreover, the purchaser may bedisadvantaged during negotiations with the seller, given that thepurchaser may not have on-site access to objective information thatwould inform the purchase decision. For these reasons, the purchaser maylack confidence that they are getting the best deal or that their otherconcerns have been adequately addressed.

SUMMARY

Implementations of the present disclosure are generally directed tofacilitating and/or optimizing a transaction, such as a purchase. Morespecifically, implementations are directed to using scanned data, suchas scanned vehicle data and/or scanned user data, to facilitate and/oroptimize a transaction.

In general, innovative aspects of the subject matter described in thisspecification can be embodied in methods that include actions of:scanning, using at least one scanning component, a vehicle tag thatencodes vehicle data describing a vehicle, and receiving, from the atleast one scanning component, the vehicle data that is retrieved byscanning the vehicle tag; scanning, using the at least one scanningcomponent, a user tag that encodes user data describing a user, andreceiving, from the at least one scanning component, the user data thatis retrieved by scanning the user tag; transmitting, over at least onenetwork, the vehicle data and the user data to a transaction serviceexecuting on at least one remote server computing device and receiving,in response, transaction data that is generated by the transactionservice based at least partly on the vehicle data and the user data, thetransaction data associated with a purchase of the vehicle by the user,the transaction data including a price of the vehicle; and presentingthe transaction data in a user interface (UI) executing on the portablecomputing device.

Implementations can optionally include one or more of the followingfeatures: the user tag is a physical credential of the user; scanningthe user tag includes capturing at least one image of the physicalcredential and performing pattern recognition to determine, as the userdata, text information including one or more of a user name and a useridentification number that is on the physical credential; the vehicletag is a printed decal affixed to the vehicle; scanning the vehicle tagincludes capturing at least one image of the printed decal andperforming pattern recognition to determine, as the vehicle data, textinformation including a vehicle identification number (VIN) that is onthe printed decal; the vehicle tag is a printed decal affixed to thevehicle, the printed decal including a scannable barcode; scanning thevehicle tag includes capturing at least one image of the scannablebarcode and decoding the scannable barcode to determine, as the vehicledata, a vehicle identification number (VIN) that is encoded in thescannable barcode; the actions further include transmitting, over the atleast one network to the transaction service, a request to purchase thevehicle, the request provided by the user through the UI executing onthe portable computing device; the actions further include receiving,from the transaction service, in response to the request to purchase thevehicle, a code that is presented in the UI, wherein entry of the codeat a kiosk causes the kiosk to dispense at least one key to the vehicle;the transaction data further includes one or more of loan information,insurance information, vehicle history information, and vehicle costinformation; and/or the price is guaranteed, by the transaction service,for a limited period of time.

Other implementations of any of the above aspects include correspondingsystems, apparatus, and computer programs that are configured to performthe actions of the methods, encoded on computer storage devices. Thepresent disclosure also provides a computer-readable storage mediumcoupled to one or more processors and having instructions stored thereonwhich, when executed by the one or more processors, cause the one ormore processors to perform operations in accordance with implementationsof the methods provided herein. The present disclosure further providesa system for implementing the methods provided herein. The systemincludes one or more processors, and a computer-readable storage mediumcoupled to the one or more processors having instructions stored thereonwhich, when executed by the one or more processors, cause the one ormore processors to perform operations in accordance with implementationsof the methods provided herein.

Implementations of the present disclosure provide one or more of thefollowing technical advantages and improvements over previouslyavailable solutions. By capturing vehicle data and/or user data byscanning physical tags associated with the vehicle and/or userrespectively, and by using the scanned data to generate transactioninformation for purchase of a vehicle, implementations provide a dataentry and transaction processing system that is more efficient, moreaccurate, and less error-prone than traditional systems that may collectthe necessary data in other ways, given the high accuracy of (e.g.,optical) scanning to recognize printed characters and/or decodescannable barcodes that include the vehicle data and/or user data.Accordingly, implementations avoid the expenditure of processing power,active memory, storage space, network capacity, and/or other computingresources that may be consumed by previously available solutions torecover from inaccuracies in entered data and/or incomplete data entry.

It is appreciated that aspects and features in accordance with thepresent disclosure can include any combination of the aspects andfeatures described herein. That is, aspects and features in accordancewith the present disclosure are not limited to the combinations ofaspects and features specifically described herein, but also include anycombination of the aspects and features provided.

The details of one or more implementations of the present disclosure areset forth in the accompanying drawings and the description below. Otherfeatures and advantages of the present disclosure will be apparent fromthe description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 depicts an example system for transaction processing, accordingto implementations of the present disclosure.

FIGS. 2-4 depict example user interfaces for transaction processing,according to implementations of the present disclosure.

FIG. 5 depicts an example kiosk for key delivery, according toimplementations of the present disclosure.

FIG. 6 depicts a flow diagram of an example process for transactionprocessing, according to implementations of the present disclosure.

FIG. 7 depicts an example computing system, according to implementationsof the present disclosure.

DETAILED DESCRIPTION

Implementations of the present disclosure are directed to facilitatingand/or optimizing a transaction, such as a purchase transaction, throughthe use of scanned data. In some implementations, a user may use theirsmartphone, tablet computer, or other computing device to scan a vehicletag that is affixed to a vehicle. The vehicle tag may be a vehicleidentification number (VIN), manufacturer label, and so forth, and mayinclude vehicle data describing the vehicle. The user may also scan auser tag or token such as a driver's license to generate user data thatidentifies the user. The vehicle data and/or user data may becommunicated, over one or more networks, to transaction service(s).Based on the received information, the service(s) may generatetransaction data that may be specific to the particular user thatprovided the vehicle data and/or user data. The transaction data mayinclude information regarding a price of the vehicle (e.g., a guaranteedprice), terms of a loan that the user may take out to finance thepurchase of the vehicle, information regarding an insurance policy forinsuring the vehicle, and so forth.

The transaction data may be presented in a user interface (UI) of anapplication executing on the user's computing device. In someimplementations, the transaction data may be presented in a scorecard inthe UI, as a summary of the price information, loan information,insurance information, and/or other information that may be employed bythe user in deciding to purchase the vehicle. If the user decides topurchase the vehicle, the UI may present one or more controls to allowthe user to indicate the purchase. Selection of such control(s) maycause the purchase transaction to be automatically completed accordingto the (e.g., guaranteed) price communicated in the transaction data.Selection of the control(s) may also indicate the user's application forthe loan, application for the insurance policy, and/or cause otheraction(s) to be performed to facilitate the user's acquisition of thevehicle. In some implementations, the completion of the purchase maycause a communication to be sent from the service(s) to the user'scomputing device. The communication may include a code that is presentedin the UI. The code may be entered at a kiosk or other device, and entryof the appropriate code may cause the kiosk to dispense one or morephysical keys that are useable to operate the vehicle.

In this way, implementations provide for a transaction process that ispartly or completely automated, such that the user may not need tointeract with a human sales person to purchase the vehicle. By providingthe transaction data that is readily available on the user's portablecomputing device, implementations enable the user to have greaterconfidence that the purchase they are making is a good value, and thatsales personnel are not taking advantage of them. Implementationsprovide service(s) that handle some or all of the purchase process forthe user. In some instances, the transaction is facilitated to such anextent that the user may not be required to negotiate (e.g., haggle) atall with any sales personnel, providing for a much more positive userexperience than in traditional sales environments where the user may beunder high pressure to buy but may not have access to objectiveinformation on which a purchase decision may be based.

FIG. 1 depicts an example system for transaction processing, accordingto implementations of the present disclosure. As shown in the example ofFIG. 1, a user 102 (e.g., a potential purchaser or customer) may operatea user device 104. In some instances, the user device 104 is a portablecomputing device such as a smartphone, tablet computer, wearablecomputer, and so forth. The user device 104 may execute an application106, which may include a UI 108. In some implementations, the UI 108 isa graphical user interface (GUI). The user device 104 may include one ormore cameras 110, which may also be described as scanning component(s)of the user device 104. The camera(s) 110 may include any suitable typeof image capture device that is configured, through optics, electronics,or both, to capture still image(s) and/or video data of a scene in afield of view in proximity to the user device 104. In someimplementations, the camera(s) 110 may be component(s) of the userdevice 104 as shown in the example of FIG. 1. Alternatively, thecamera(s) 110 may be external to the user device 104 and may communicateimage data and/or other information to the application 106 using one ormore wired and/or wireless connections, such as a Bluetooth™ connectionor other type of wireless network connection. The camera(s) 110 maycapture image(s) and/or video data in a visible range of wavelengthsand/or in a wavelength range that is outside the visible range (e.g.,infrared).

In some instances, the user 102 may be in a product sales environmentsuch as an automobile dealership, showroom, sales lot, and so forth. Theuser 102 may be perusing a vehicle 112 as a possible purchase. The user102 may employ the camera(s) 110 to scan a vehicle tag 114 and retrievevehicle data 122 from the tag 114. In some instances, the tag 114 is avehicle identification number (VIN) affixed to the vehicle 112. The VINmay uniquely identify the vehicle 112 amongst a plurality of vehicles.In some instances, the tag 114 may be a manufacturer sticker and/ordecal that is affixed to the vehicle 114, and that presents informationregarding the vehicle 112 such as the make, model, year, color, trimoptions, mileage, manufacturer's suggested retail price (MSRP), seller'sactual price, and so forth. The camera(s) 110 may generate image(s) ofthe tag 114 which are provided to the application 106. The application106 may analyze the image(s) and retrieve vehicle data 112 from theimage(s). The vehicle data 122 retrieved from the vehicle tag 114 mayinclude, but is not limited to: a VIN; the make, model, and/or year ofthe vehicle; trim and/or option details for the particular vehicle; andso forth. In some instances, the user device 104 may capture image(s) ofthe vehicle 112 as a whole and/or portion(s) of the vehicle 112, e.g.,from various viewpoints, and the image(s) may be analyzed to identifythe vehicle's make, mode, year, trim options, and so forth. Scanning ofimage of the vehicle may be performed in instances when a scannablevehicle tag 114 is not present and/or not accessible for scanning.

The camera(s) 110 may also be used to scan a user tag 116. The user tag116 may be an identification card or other type of physical credentialthat is uniquely associated with, and/or that identifies, the user 102,such as a driver's license, passport, military identification card,other type of government-issued identification card, printed bill,student identification card, and so forth. The user tag 116 may bescanned to extract user data 124 from the user tag 116, such as theuser's name (e.g., first, last, and/or middle name), identificationnumber, physical address, email address, phone number, and/or otheridentifying information.

Implementations support the use of various suitable techniques forscanning the tags 114 and/or 116 to extract the vehicle data 122 anduser data 124 respectively. In some implementations, image(s) of thetag(s) may be captured and analyzed using optical character recognition(OCR) or other types of pattern recognition to determine alphanumericcharacters, symbols, words, and/or sequences of characters, symbols,and/or words present in the tag(s). In some implementations, the tag(s)may include barcode(s) that are scannable to retrieve data that isencoded into the barcode(s). Such barcode(s) may employ any suitableencoding format. The barcode(s) may be one-dimensional barcode(s), suchas universal product codes (UPCs). The barcode(s) may also bemulti-dimensional barcode(s) and/or matrix barcode(s), such as a quickresponse (QR) codes. In some instances, the tag(s) may include radiofrequency identification (RFID) and/or near field communication (NFC)tag(s) that emit a radio frequency signal, e.g., in response to receivea triggering and/or interrogating signal, which may also be described asan activation signal. In such instances, the signal(s) emitted from thetag(s) may include information such as the vehicle data 122 and/or userdata 124, and scanning the tag(s) may include sending an interrogatingsignal from the user device 104, and receiving and processing thetag-emitted signals to determine the vehicle data 122 and/or user data124.

One or both of the vehicle data 122 and/or the user data 124 may becommunicated from the application 106, over one or more networks, totransaction service(s) 120 executing on one or more server devices 118.The server device(s) 118 may include any suitable number and type ofcomputer device(s). Based at least partly on the vehicle data 122 and/oruser data 124, the service(s) 120 may generate transaction data 126 thatis particular to the user 102 and/or the vehicle 112. The transactiondata 126 may include, but is not limited to, one or more of thefollowing.

Price information, describing a price to purchase the vehicle 112. Insome instances, the price may be a guaranteed price, such that thesending of the transaction data 126 is a guarantee that the user 102 maypurchase the vehicle 112 at the price for a certain period of time thatis limited. For example, the guarantee may hold the price of the vehicle112 for up to 24 hours, such that the user may purchase the vehicle atthat price at any time within 24 hours from the time when the priceguarantee is provided to the user. After that time, if the user wishesto purchase the vehicle, the purchase may not be possible at thepreviously guaranteed price. The guaranteed price information may beprovided for the vehicle 112 that the user 102 is currently examining(e.g., having the scanned vehicle tag) and/or other nearby vehicleswithin a range specified by the user 102 through the UI 108.

Loan information, describing the terms of a loan that the user 102 maytake out to finance their purchase of the vehicle 112. The loaninformation may include an amount of the loan, a payoff amount, aninterest rate, monthly payments (e.g., principal and/or interestpayments), a term of the loan (e.g., number of months to pay off theloan), an indication of the financial institution providing and/orservicing the loan, and so forth. The sending of the transaction data126 may be an offer of the loan (e.g., the user having pre-qualified forthe loan), under the described terms, from the service(s) 120 (or from afinancial institution that manages the services) to the user 102.

Insurance information, describing the terms of an insurance policy thatthe user 102 may take out to insure the vehicle 112. The insuranceinformation may include terms such amount(s) of property damage and/orinjury coverage, premiums, deductibles, time period for the policy,conditions on the policy, and so forth. The sending of the transactiondata 126 may be an offer of the insurance policy (e.g., the user havingpre-qualified for the policy), under the described terms, from theservice(s) 120 (or from an insurance provider that manages the services)to the user 102.

Vehicle history information, describing a history of repairs,maintenance, parts replacement, accidents, prior ownership, and/or otherinformation regarding the history of the vehicle 112.

Vehicle cost information, including estimated maintenance, repair,and/or operating costs of the vehicle 112 for a period of time in thefuture. Such cost information may include fuel costs, costs to replaceengine components, tires, or other parts of the vehicle, estimatedmaintenance costs based on the costs of other vehicles of the same make,model, year, and/or other characteristics, and so forth. Suchinformation may provide a total (e.g., monthly, yearly, etc.) cost ofownership for the vehicle in the future.

Other vehicle information, including the availability and/or price ofother instances of the same and/or similar vehicle at other (e.g.,nearby) sellers. In some implementations, the UI 108 may enable the user102 to specify a distance or range to search for similar nearbyvehicles, e.g., within 5 miles of the current location, within 50 milesof the current location, and so forth. Implementations may employ anysuitable technique for determining the current location of the user 102and/or the user device 104. For example, location may be determinedusing a satellite-based navigation system such as the global positioningsystem (GPS). The current vehicle 112 and/or the other (e.g., nearby)vehicle(s) may include new vehicle(s), used vehicle(s), and/or both newand used vehicle(s). The current vehicle 112 and/or the other vehicle(s)may include vehicle(s) that are available for purchase and/or vehicle(s)that are available for rental or lease.

Although examples herein may describe and/or depict vehicles asautomobiles, implementations are not so limited. Vehicle(s) may includeautomobiles, motorcycles, mopeds, campers, recreational vehicles,off-road vehicles, watercraft, aircraft, and/or other types of vehicles.Moreover, the implementations described herein may also be used tofacilitate and/or optimize transactions to purchase or otherwise acquireother types of consumer products, including but not limited to homeelectronics, appliances, real property (e.g., houses or otherstructures), and so forth.

In some implementations, the user 102 may be required to login to theapplication 106, and be authenticated as an authorized user of theapplication, using credential(s) such as a login name, password,personal identification number (PIN), biometric data, and so forth. Insuch implementations, the user data 124 may be determined based at leastpartly on the identity of the user 102 who is logged into theapplication. In some implementations, the scannable user tag 116 may beemployed to generate the user data 124 that identifies the user 102instead of relying on the user 102 being logged into the application106. For example, the size of the application 106 may be minimized,and/or the user experience more streamlined, through use of thescannable user tag 116 instead of requiring the user 102 to log in.

In some implementations, the user data 124 may be employed to generate(e.g., prepopulate) a loan application based on the particular financialcharacteristics or other characteristics of the user 102, such as theircredit history, credit score, current lines of credit, employment, andso forth. The user data 124 may also be employed to generate aninsurance policy application based on the particular characteristics ofthe user 102, such as their driving history, location, vehicle usagepatterns (e.g., number of miles driven per year), whether the vehicle isto be used for personal and/or commercial purposes, and so forth. Theloan application and/or insurance application may be provided to theuser 102 in the transaction data 126.

In some implementations, the UI 108 may present at least a portion ofthe received transaction data 126 in a scorecard that provides the user102 with a summary of the information regarding the vehicle 112 to bepurchased, price (e.g., guaranteed price), loan information (e.g.,interest rate, payoff term, etc.) insurance information, total cost ofownership, and so forth. In some implementations, the scorecard mayprovide multiple sets of information to compare different vehicles,e.g., in a side-by-side comparison. In some instances, the seller of thevehicle 112 may provide a counter-offer with regard to the loan,purchase price, and/or other information. In such instances, thescorecard may enable the user 102 to enter the counter-offer informationprovided by the dealer to compare with the information provided by theservice(s) 120. The service(s) 120 may also update the transaction data126, e.g., as a counter to the seller's counter-offer, and thatinformation may also be presented in the scorecard. In this way,implementations provide a connection to the service(s) 120 while theuser 102 is negotiating with the seller, e.g., to ensure that the user102 is provided with the best possible deal.

In some implementations, the server device(s) 118 execute one or moreexternal service application protocol interfaces (APIs) 128 to enablethe server device(s) 118 to request information from external services.For example, the API(s) 128 may be employed to retrieve, from externalservice(s), price information for a vehicle (e.g., a guaranteed price),repair and/or maintenance history for the vehicle 112, financialinformation regarding the user 102 (e.g., to be used to generate theloan application), and so forth. In some implementations, instead of orin addition to using an external API 128 to determine price informationfor a vehicle, and/or other information regarding the vehicle, a localmodel may be employed to determine such information. For example, theserver device(s) 118 may access a model that outputs an estimated pricefor a vehicle based on input of a make, model, and year of the vehicleand/or based on default trim options for the vehicle. Local model(s) mayalso be employed to determine estimated maintenance and/or repair costs,estimated fuel costs, and so forth, for the vehicle.

Through the integration of loan application processing, insuranceapplication processing, pricing data (e.g., for a guaranteed vehicleprice), and/or other information, implementations provide a seamlessand/or expedited process for purchasing a vehicle or other item. Thisprocess may be personalized for the particular user 102, e.g., the loaninformation, insurance information, and/or other transaction data 126may be particularly generated for and tailored to the user 102. Theimplementations described herein may be employed to provide the user 102with a seamless, hassle-free, vehicle buying experience that may involveless negotiation than traditional vehicle buying experiences. In someimplementations, the vehicle 112 may be purchased without requiring theuser 102 to negotiate and/or haggle with a seller and/or sales personnelat a dealership. In some implementations, the system may include a kioskor other device that dispenses one or more keys to the user 102 if theuser 102 completes the purchase, as described further below.

FIGS. 2-4 depict examples of the UI 108 that may be used for transactionprocessing, according to implementations of the present disclosure. Inthe example of FIG. 2, the UI 108 is presenting a set of features (alsodescribed as options) available through the application 106.

The “Find a Vehicle” option 202 may present a list of vehicles that areavailable for purchase within a user-specified range or distance. Thelist of vehicles may be generated in response to search criteriaspecified by the user, such as make, model, year, color, price range,distance, type of vehicle, engine type, new or used vehicles, and/orother options.

The “Scan VIN” option 204 may be used to scan the tag 114 on aparticular vehicle 112, e.g., if the user is located near a vehicle at ashowroom or other sales location.

The “Get Insurance Quote” option 206 may be used to request that aninsurance policy quote be generated for the user 102 for a particularselected or scanned vehicle 112.

The “Apply for a Loan” option 208 may be used to request that a loanapplication be generated for the user 102 to finance the purchase of aparticular vehicle 112 or a particular price of a vehicle. In someinstances, the user 102 may specify criteria for a loan, such as theparticular monthly payment they wish to pay, and the loan applicationmay be generated based on the user-specified criteria, purchase price ofthe vehicle, financial data regarding the user 102, and so forth.

The “Loan Calculators” option 210 may be used to access one or more loancalculators to estimate monthly payments, total cost of the loan, and/orother loan characteristics based on inputs such as a purchase price,interest rate, term of the loan, and so forth.

The “Dealership Prep Kit” option 212 may be used to access variousfeatures that allow the user 102 to prepare for visiting a dealership,such as a set of questions that may be asked of the dealer, add-ons towatch out for (e.g., undercoating, extended warranties, etc.), and soforth.

The “Maintain” option 214 may be used to access various featuresregarding the maintenance of a vehicle, such as requesting roadsideassistance, repairs, rental vehicles, and so forth.

The “Sell a Vehicle” option 216 may be used to access features to assistthe user 102 in selling a vehicle.

FIG. 3 depicts an example UI 108 in which the user 102 is scanning a tag114 on a vehicle 112. In this example, the tag 114 is a printed stickerand/or decal affixed to the vehicle 112, describing characteristics ofthe vehicle 112. The tag 114 may be optically scanned (e.g., usingcamera(s) 110) and presented in the UI 108. In some implementations, theapplication 106 may analyze the tag 114 to extract vehicle data 122 fromthe tag 114 such as using OCR to extract text data, scanning a barcode(e.g., UPC, QR code, or other scannable code) to extract data encoded inthe barcode, and so forth.

FIG. 4 depicts an example UI 108 in which the user 102 is viewingtransaction data 126 for a particular vehicle 112, such as the vehicle112 for which the tag 114 was scanned as in FIG. 3. The UI 108 maypresent a price for the vehicle 112. The price may be a guaranteedprice, as described above. The UI 108 may also present a scorecard 402describing particular aspects of the transaction data 126. In theexample shown, the scorecard 402 is presenting an estimated loan paymentfor a loan to finance the vehicle purchase, insurance information suchas total loss protection, debt protection, extended vehicle protection,and an estimated insurance payment. The UI 108 may present control(s)404 that enable the user 102 to purchase the vehicle 112 shown in the UI108, or opt not to make the purchase (e.g., “No Thanks”).

In some implementations, the scorecard 402 provides for the user asummary or digest of information that is relevant to the user's purchaseand ongoing ownership of the vehicle. For example, the scorecard 402 maypresent a summary of the insurance coverage for the car, including thetypes of coverage (e.g., collision, uninsured motorist, debt protection,total loss protection, extended vehicle protection, etc.) and/or costsof the coverage (e.g., monthly premiums, deductibles, limits or lackthereof, etc.). The scorecard 402 may also present a summary of the costof purchasing the vehicle, including terms of a loan such as interestrate and/or monthly payments to be paid on the loan. The scorecard 402may also present a summary of other costs of owning the vehicle, such asone or more of the following: expected maintenance and/or repair costsgiven the make, model, and year of the vehicle, determined based on arequest to an external API and/or through a maintenance and/or repaircost prediction model; expected fuel costs given the make, model, andyear of the vehicle, and/or given information regarding the user'sexpected usage for the vehicle (e.g., daily commutes to work, longcross-country drives, participation in a ridesharing service, etc.);depreciation costs, given the make, model, and year of the vehicle, andbased on information describing expected depreciation in the value ofthe vehicle (e.g., resale value) over time. Accordingly, the scorecard402 may provide a total cost of ownership (TCO) of the vehicle, such asa total monthly cost of owning the vehicle, including a sum of themonthly loan payment, monthly insurance premium, monthly fuel costs, andexpected monthly maintenance and/or repair costs. TCO may be determinedper month, as described above, or for any other appropriate periodicity(e.g., yearly cost of ownership, etc.).

FIG. 5 depicts an example kiosk 500 for key delivery, according toimplementations of the present disclosure. If the user 102 opts topurchase the vehicle 112, e.g., through the UI 108 as shown in FIG. 4, acode may be communicated from the service(s) 120 to the user device 104and the code may be presented in the UI 108. A signal may also be sentto the kiosk 500 to indicate that the particular code is associated withthe particular vehicle 112 that has been purchased. The user 102 mayenter the code into an interface 502 of the kiosk 500, e.g., keyboard,touchscreen, display, etc. If the correct code is entered, the key(s)for the vehicle 112 may be dispensed by the kiosk 500 through a keydispenser opening 504. The user 102 may retrieve the key(s) and use thekey(s) to access and operate the vehicle 112. In this way,implementations enable the user 102 to purchase a vehicle 112, arrangefinancing for the vehicle 112, insure the vehicle 112, and drive thevehicle 112 off the sales lot without ever needing to speak with a salesrepresentative.

FIG. 6 depicts a flow diagram of an example process for transactionprocessing, according to implementations of the present disclosure.Operations of the process may be performed by one or more of theapplication 106, the UI 108, the transaction service(s) 120, theexternal service API(s) 128, and/or other software module(s) executingon the user device 104, the server device(s) 118, or elsewhere.

The vehicle tag 114 may be scanned (602) to determine the vehicle data122, as described above.

The vehicle data 122, e.g., a VIN, may be communicated (604) to theservice(s) 120 from the user device 104. Based on the vehicle data 122,the service(s) 120 may generate and send (606) price information,information regarding other similar vehicles that are nearby, and/orother types of transaction data 126.

The transaction data 126 may be sent (606) to the user device 104 andpresented (608) in the UI 108, e.g., in the scorecard 402.

The user tag 116 may be scanned (610) to determine the user data 124, asdescribed above.

The user data 124 may be communicated (612) to the service(s) 120 fromthe user device 104. Based on the user data 124 and/or vehicle data 122,the service(s) 120 may generate and send (614) loan information,insurance information, and/or other transaction data 126 to facilitatethe user's purchase of the vehicle 112.

The transaction data 126 may be sent (614) to the user device 104 andpresented (616) in the UI 108, e.g., in the scorecard 402. Based on thepresented transaction data 126 in the UI 108, the user 102 may select topurchase the vehicle 112, not purchase the vehicle 112, compare thecurrent vehicle 112 to other vehicles, request more information, requestmodification of the loan terms, insurance policy, and/or other aspectsof the transaction data 126, and/or put off the decision to anothertime.

FIG. 7 depicts an example computing system, according to implementationsof the present disclosure. The system 700 may be used for any of theoperations described with respect to the various implementationsdiscussed herein. For example, the system 700 may be included, at leastin part, in one or more of the user device(s) 104, server device(s) 118,and/or other computing device(s) or system(s) described herein. Thesystem 700 may include one or more processors 710, a memory 720, one ormore storage devices 730, and one or more input/output (I/O) devices 750controllable through one or more I/O interfaces 740. The variouscomponents 710, 720, 730, 740, or 750 may be interconnected through atleast one system bus 760, which may enable the transfer of data betweenthe various modules and components of the system 700.

The processor(s) 710 may be configured to process instructions forexecution within the system 700. The processor(s) 710 may includesingle-threaded processor(s), multi-threaded processor(s), or both. Theprocessor(s) 710 may be configured to process instructions stored in thememory 720 or on the storage device(s) 730. The processor(s) 710 mayinclude hardware-based processor(s) each including one or more cores.The processor(s) 710 may include general purpose processor(s), specialpurpose processor(s), or both.

The memory 720 may store information within the system 700. In someimplementations, the memory 720 includes one or more computer-readablemedia. The memory 720 may include any number of volatile memory units,any number of non-volatile memory units, or both volatile andnon-volatile memory units. The memory 720 may include read-only memory,random access memory, or both. In some examples, the memory 720 may beemployed as active or physical memory by one or more executing softwaremodules.

The storage device(s) 730 may be configured to provide (e.g.,persistent) mass storage for the system 700. In some implementations,the storage device(s) 730 may include one or more computer-readablemedia. For example, the storage device(s) 730 may include a floppy diskdevice, a hard disk device, an optical disk device, or a tape device.The storage device(s) 730 may include read-only memory, random accessmemory, or both. The storage device(s) 730 may include one or more of aninternal hard drive, an external hard drive, or a removable drive.

One or both of the memory 720 or the storage device(s) 730 may includeone or more computer-readable storage media (CRSM). The CRSM may includeone or more of an electronic storage medium, a magnetic storage medium,an optical storage medium, a magneto-optical storage medium, a quantumstorage medium, a mechanical computer storage medium, and so forth. TheCRSM may provide storage of computer-readable instructions describingdata structures, processes, applications, programs, other modules, orother data for the operation of the system 700. In some implementations,the CRSM may include a data store that provides storage ofcomputer-readable instructions or other information in a non-transitoryformat. The CRSM may be incorporated into the system 700 or may beexternal with respect to the system 700. The CRSM may include read-onlymemory, random access memory, or both. One or more CRSM suitable fortangibly embodying computer program instructions and data may includeany type of non-volatile memory, including but not limited to:semiconductor memory devices, such as EPROM, EEPROM, and flash memorydevices; magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. In some examples,the processor(s) 710 and the memory 720 may be supplemented by, orincorporated into, one or more application-specific integrated circuits(ASICs).

The system 700 may include one or more I/O devices 750. The I/Odevice(s) 750 may include one or more input devices such as a keyboard,a mouse, a pen, a game controller, a touch input device, an audio inputdevice (e.g., a microphone), a gestural input device, a haptic inputdevice, an image or video capture device (e.g., a camera), or otherdevices. In some examples, the I/O device(s) 750 may also include one ormore output devices such as a display, LED(s), an audio output device(e.g., a speaker), a printer, a haptic output device, and so forth. TheI/O device(s) 750 may be physically incorporated in one or morecomputing devices of the system 700, or may be external with respect toone or more computing devices of the system 700.

The system 700 may include one or more I/O interfaces 740 to enablecomponents or modules of the system 700 to control, interface with, orotherwise communicate with the I/O device(s) 750. The I/O interface(s)740 may enable information to be transferred in or out of the system700, or between components of the system 700, through serialcommunication, parallel communication, or other types of communication.For example, the I/O interface(s) 740 may comply with a version of theRS-232 standard for serial ports, or with a version of the IEEE 1284standard for parallel ports. As another example, the I/O interface(s)740 may be configured to provide a connection over Universal Serial Bus(USB) or Ethernet. In some examples, the I/O interface(s) 740 may beconfigured to provide a serial connection that is compliant with aversion of the IEEE 1394 standard.

The I/O interface(s) 740 may also include one or more network interfacesthat enable communications between computing devices in the system 700,or between the system 700 and other network-connected computing systems.The network interface(s) may include one or more network interfacecontrollers (NICs) or other types of transceiver devices configured tosend and receive communications over one or more networks using anynetwork protocol.

Computing devices of the system 700 may communicate with one another, orwith other computing devices, using one or more networks. Such networksmay include public networks such as the internet, private networks suchas an institutional or personal intranet, or any combination of privateand public networks. The networks may include any type of wired orwireless network, including but not limited to local area networks(LANs), wide area networks (WANs), wireless WANs (WWANs), wireless LANs(WLANs), mobile communications networks (e.g., 3G, 4G, Edge, etc.), andso forth. In some implementations, the communications between computingdevices may be encrypted or otherwise secured. For example,communications may employ one or more public or private cryptographickeys, ciphers, digital certificates, or other credentials supported by asecurity protocol, such as any version of the Secure Sockets Layer (SSL)or the Transport Layer Security (TLS) protocol.

The system 700 may include any number of computing devices of any type.The computing device(s) may include, but are not limited to: a personalcomputer, a smartphone, a tablet computer, a wearable computer, animplanted computer, a mobile gaming device, an electronic book reader,an automotive computer, a desktop computer, a laptop computer, anotebook computer, a game console, a home entertainment device, anetwork computer, a server computer, a mainframe computer, a distributedcomputing device (e.g., a cloud computing device), a microcomputer, asystem on a chip (SoC), a system in a package (SiP), and so forth.Although examples herein may describe computing device(s) as physicaldevice(s), implementations are not so limited. In some examples, acomputing device may include one or more of a virtual computingenvironment, a hypervisor, an emulation, or a virtual machine executingon one or more physical computing devices. In some examples, two or morecomputing devices may include a cluster, cloud, farm, or other groupingof multiple devices that coordinate operations to provide loadbalancing, failover support, parallel processing capabilities, sharedstorage resources, shared networking capabilities, or other aspects.

Implementations and all of the functional operations described in thisspecification may be realized in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Implementations may be realized asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a computer readable medium forexecution by, or to control the operation of, data processing apparatus.The computer readable medium may be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more of them. The term “computing system” encompasses allapparatus, devices, and machines for processing data, including by wayof example a programmable processor, a computer, or multiple processorsor computers. The apparatus may include, in addition to hardware, codethat creates an execution environment for the computer program inquestion, e.g., code that constitutes processor firmware, a protocolstack, a database management system, an operating system, or acombination of one or more of them. A propagated signal is anartificially generated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal that is generated to encodeinformation for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) may be written in any appropriate form ofprogramming language, including compiled or interpreted languages, andit may be deployed in any appropriate form, including as a standaloneprogram or as a module, component, subroutine, or other unit suitablefor use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program may bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program may be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification may beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows may also be performedby, and apparatus may also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any appropriate kind of digital computer.Generally, a processor may receive instructions and data from a readonly memory or a random access memory or both. Elements of a computercan include a processor for performing instructions and one or morememory devices for storing instructions and data. Generally, a computermay also include, or be operatively coupled to receive data from ortransfer data to, or both, one or more mass storage devices for storingdata, e.g., magnetic, magneto optical disks, or optical disks. However,a computer need not have such devices. Moreover, a computer may beembedded in another device, e.g., a mobile telephone, a personal digitalassistant (PDA), a mobile audio player, a Global Positioning System(GPS) receiver, to name just a few. Computer readable media suitable forstoring computer program instructions and data include all forms ofnon-volatile memory, media and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory may be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, implementations may be realizedon a computer having a display device, e.g., a CRT (cathode ray tube) orLCD (liquid crystal display) monitor, for displaying information to theuser and a keyboard and a pointing device, e.g., a mouse or a trackball,by which the user may provide input to the computer. Other kinds ofdevices may be used to provide for interaction with a user as well; forexample, feedback provided to the user may be any appropriate form ofsensory feedback, e.g., visual feedback, auditory feedback, or tactilefeedback; and input from the user may be received in any appropriateform, including acoustic, speech, or tactile input.

Implementations may be realized in a computing system that includes aback end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront end component, e.g., a client computer having a graphical UI or aweb browser through which a user may interact with an implementation, orany appropriate combination of one or more such back end, middleware, orfront end components. The components of the system may be interconnectedby any appropriate form or medium of digital data communication, e.g., acommunication network. Examples of communication networks include alocal area network (“LAN”) and a wide area network (“WAN”), e.g., theInternet.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular implementations. Certain features that are described in thisspecification in the context of separate implementations may also beimplemented in combination in a single implementation. Conversely,various features that are described in the context of a singleimplementation may also be implemented in multiple implementationsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination may in some examples be excised from the combination, andthe claimed combination may be directed to a sub-combination orvariation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemsmay generally be integrated together in a single software product orpackaged into multiple software products.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. For example, various formsof the flows shown above may be used, with steps re-ordered, added, orremoved. Accordingly, other implementations are within the scope of thefollowing claims.

What is claimed is:
 1. A computing system comprising: at least oneprocessor; and memory communicatively coupled to the at least oneprocessor, the memory storing instructions which, when executed by theat least one processor, instruct the at least one processor to performoperations comprising: receiving vehicle data associated with a vehicle,wherein the vehicle data is retrieved through a scan, by at least onescanning component, of a vehicle tag that includes the vehicle data;transmitting, over at least one network, the vehicle data to at leastone transaction service executing on at least one remote servercomputing device; receiving transaction data that is generated by the atleast one transaction service based at least partly on the vehicle data,wherein the transaction data represents a transaction associated withthe vehicle; and presenting the transaction data in a user interface(UI).
 2. The computing system of claim 1, the operations furthercomprising: transmitting, over the at least one network to the at leastone transaction service, a request to purchase the vehicle, the requestprovided through the UI.
 3. The computing system of claim 1, theoperations further comprising: transmitting, over the at least onenetwork, user data to the at least one transaction service, wherein theuser data is associated with a purchaser of the vehicle, and wherein thetransaction data is generated by the at least one transaction servicefurther based on the user data.
 4. The computing system of claim 3,wherein the user data is retrieved through a scan, by the at least onescanning component, of a user tag that includes the user data.
 5. Thecomputing system of claim 1, wherein the transaction data includes oneor more of vehicle history information, vehicle cost information,insurance information, or price information regarding the vehicle. 6.The computing system of claim 1, wherein: the at least one transactionservice includes a first transaction service and a second transactionservice; the vehicle data is received by the first transaction serviceand communicated to the second transaction service which, in response,determines a price of the vehicle based on the vehicle data andcommunicates the price to the first transaction service; and the firsttransaction service generates the transaction data based at least on theprice.
 7. The computing system of claim 1, wherein the transaction datais valid for a limited period of time.
 8. A computer-implemented methodperformed by at least one processor, the method comprising: receiving,by the at least one processor, vehicle data associated with a vehicle,wherein the vehicle data is retrieved through a scan, by at least onescanning component, of a vehicle tag that includes the vehicle data;transmitting, by the at least one processor, over at least one network,the vehicle data to at least one transaction service executing on atleast one remote server computing device; receiving, by the at least oneprocessor, transaction data that is generated by the at least onetransaction service based at least partly on the vehicle data, whereinthe transaction data represents a transaction associated with thevehicle; and presenting, by the at least one processor, the transactiondata in a user interface (UI).
 9. The method of claim 8, furthercomprising: transmitting, by the at least one processor, over the atleast one network to the at least one transaction service, a request topurchase the vehicle, the request provided through the UI.
 10. Themethod of claim 8, further comprising: transmitting, by the at least oneprocessor, over the at least one network, user data to the at least onetransaction service, wherein the user data is associated with apurchaser of the vehicle, and wherein the transaction data is generatedby the at least one transaction service further based on the user data.11. The method of claim 10, wherein the user data is retrieved through ascan, by the at least one scanning component, of a user tag thatincludes the user data.
 12. The method of claim 8, wherein thetransaction data further includes one or more of vehicle historyinformation, vehicle cost information, insurance information, or priceinformation regarding the vehicle.
 13. The method of claim 8, wherein:the at least one transaction service includes a first transactionservice and a second transaction service; the vehicle data is receivedby the first transaction service and communicated to the secondtransaction service which, in response, determines a price of thevehicle based on the vehicle data and communicates the price to thefirst transaction service; and the first transaction service generatesthe transaction data based at least on the price.
 14. One or morenon-transitory computer-readable media storing instructions which, whenexecuted by at least one processor, cause the at least one processor toperform operations comprising: receiving vehicle data associated with avehicle, wherein the vehicle data is retrieved through a scan, by atleast one scanning component, of a vehicle tag that includes the vehicledata; transmitting, over at least one network, the vehicle data to atleast one transaction service executing on at least one remote servercomputing device; receiving transaction data that is generated by the atleast one transaction service based at least partly on the vehicle data,wherein the transaction data represents a transaction associated withthe vehicle; and presenting the transaction data in a user interface(UI).
 15. The one or more non-transitory computer-readable media systemof claim 14, the operations further comprising: transmitting, over theat least one network to the at least one transaction service, a requestto purchase the vehicle, the request provided through the UI.
 16. Theone or more non-transitory computer-readable media system of claim 14,the operations further comprising: transmitting, over the at least onenetwork, user data to the at least one transaction service, wherein theuser data is associated with a purchaser of the vehicle, and wherein thetransaction data is generated by the at least one transaction servicefurther based on the user data.
 17. The one or more non-transitorycomputer-readable media system of claim 16, wherein the user data isretrieved through a scan, by the at least one scanning component, of auser tag that includes the user data.
 18. The one or more non-transitorycomputer-readable media system of claim 14, wherein the transaction dataincludes one or more of vehicle history information, vehicle costinformation, insurance information, or price information regarding thevehicle.
 19. The one or more non-transitory computer-readable mediasystem of claim 14, wherein: the at least one transaction serviceincludes a first transaction service and a second transaction service;the vehicle data is received by the first transaction service andcommunicated to the second transaction service which, in response,determines a price of the vehicle based on the vehicle data andcommunicates the price to the first transaction service; and the firsttransaction service generates the transaction data based at least on theprice.
 20. The one or more non-transitory computer-readable media systemof claim 14, wherein the transaction data is valid for a limited periodof time.